Problem solved-ish. The EventSub-over-WebSocket system relies on the low-level protocol’s ping/pong, rather than any software-level client-side communication. And of course, if a socket in JS is not completely closed and the variable reference to it gets overwritten before it does, the connection is left dangling, but the browser keeps on PONG-ing silently in the background for as long as the page is open.