TCP socket doesn't get closed on close_handshake_timeout when TLS is used

[mstaz]

Hello,
I'm still using WebSocket++ 0.7.0 with wolfSSL instead of OpenSSL. For TLS client connections I noticed that the TCP socket doesn't get closed when the close handshake fails. Means the server doesn't close the underlying TCP connection which causes the handle_close_handshake_timeout to be executed. However only SSL_shutdown is called what causes a TLS close notify message, but the TCP connection stays alive.
Is it expected that SSL_shutdown closes the underyling connection?

I could solve this by registering a termination handler and there calling:
connection->get_raw_socket().cancel();
Is this okay or will it break something?

Thanks,
Max