How to detect a connection ungracefully closed by a client

I noticed that a crash of the web browser (client side) that initiated a webocket connection does not trigger a kill of the script (I'am using bash) that was started by the websocket server at connection time, despite the existence of a ping-pong mechanism that could be used to detect and cure such a scenario.
How can we otherwise handle that scenario?