Dead WebSocket connections could be killed after a silence deadline, but nothing sets one.
A keepalive deadline that terminates silent sockets exists but no connection configures it in this build.
What's wrong with this entry?
The WebSocket monitor's keepalive gained a deadline: if no message arrives within it, the socket is terminated rather than pinged again. The only keepalive configuration in this build supplies opening frames, the ping frame and an interval, and no deadline, so no connection currently uses this.
openFrames
Strings lifted out of the shipped bundle, so the claim above can be checked against them.