Deployment slots use the same port bindings with regional VNet integration

It appears that when regional VNet integration is enabled, deployment slots start sharing the same port bindings. If your application creates a port binding then when a second deployment slot is started the application will no longer be able to create the port binding as the port is in use. This means that each slot has to have a different configuration in terms of what ports it listens on.

This only occurs when the VNet integration is enabled, when it is disconnected the conflict no longer occurs.

I guess this is why PORT and SSH_PORT are currently being set dynamically. Is the above limitation also going to be removed when the feature becomes generally available?