Vaadin Dialog overlay retention causing client‑side memory growth

Vaadin Dialog overlays are expected to be fully disposed after the dialog is closed, yet repeated open/close cycles can cause client‑side memory growth.

The goal is to verify whether the overlay component retains a reference to the dialog after closure, which may lead to a memory leak in Chrome DevTools heap snapshots. Testing must be performed on a supported Vaadin version (e.g., 14) using Chrome DevTools, and results may differ on newer releases or other browsers. Does the overlay retain a reference to the dialog after close in Vaadin 14? Is the memory growth reproducible when opening and closing the dialog multiple times?