Why is my session lost with mendix 7 during a zero-down-time deploy

We are experimenting with Bluemix cloud foundry. In our experiment we are horizontally scaling and doing zero-down-time deploy's. According to the documentation in Mendix 7 it is no longer needed to store sessions in an external store.  (https://github.com/mendix/cf-mendix-buildpack#configuring-clustering-for-mendix-7) Though our experiance is that we loose our session during a zero-down-time deploy. Is that expected?
1 answers

Yes, that is expected.

If you deploy a new version of your project, it may contain domain model changes: new or altered entities and non-persistent entities.

The mendix client retrieves information about your domain model from the server. Based on this it keeps state in the browser.  If your domain model changes, the state in the client may no longer match your new project definition.

For example: if you change an attribute from read/write to read, the client needs to start including a hash to proof that the attribute was not changed. If it would communicate based on the old model an error would be thrown.

To avoid client errors we refresh the client. Technically, it's still the same session though.