You can likely get around that by deploying to different context paths instead of, or in addition to, different ports (the problem sounds a bit like a bug though, or unnecessary restriction).
You will then run in the real problem though, which is loading the same web components (e.g. vaadin-button) twice in the browser.