Nature of sessions and driver reconnect allow bytecode transactions to appear to remain open

The driver is design to reconnect if it loses its connection to the server. For sessions a close can happen if there is a timeout on the session itself. On the server the session is invalidated, but on the client side, it tries to reconnect using the same session id. Unfortunately this reconnect creates a scenario for bytecode transactions where it can appear as though you're working the same transaction when you are not.

Test to demonstrate shown here