Multiple websocket instances accumulating in the browser after reconnection

[hally9k]

We have an interesting issue we are observing when triggering a reconnection scenario by killing the server.
The connection comes back up correctly but each reconnection that happens results in an additional websocket instance being held in the browser.

Here is a simple Repro:
https://github.com/hally9k/subscription-transport-ws-repro

Does this accumulation of websocket instances represent a memory leak?

For a long running application on potentially shady network connections this appears as though it would absorb more and more resource for every successful reconnection.

Is the dev tools maybe holding onto a reference of the WS? 🤔