WebSocketChannel: idle channel not closed

As far as I understand, the timeout behavior of a WebSocketChannel is to send a CLOSE frame, and then only close the underlying socket if the client closes the socket or sends a CLOSE frame. [edit: links updated]

This seems to leak resources when malicious or buggy clients never close the underlying TCP connection and never send a CLOSE frame. I believe it would be desirable for Undertow servers to control their own fate and eventually close channel and thus socket forcefully; what is your position on this behavior?