Asynchronous TCP Session Closure Causes New Session to Close

[jkralik]

Description

Currently, closing the TCP session is asynchronous. This leads to a situation where when the event thread closes a TCP-TLS session and then creates a new one for the same session, the asynchronous event indicating that the TCP session has closed causes the new session to also close. This issue arises because we are unable to distinguish between the old and new sessions.

Steps to Reproduce

1. Close a TCP-TLS session asynchronously.
2. Immediately create a new TCP-TLS session for the same connection.
3. Observe that the new session is closed unexpectedly due to the asynchronous event from the old session closure.

Expected Behavior

The new TCP-TLS session should remain open and not be affected by the asynchronous closure event of the old session.