It might happen that, when a DisposableCommand.dispose is invoked, the calling transaction is still active, and in that case, the lock associated to the runtimemanager is not released.
For that case, and that case only, it will be good to skip the transaction status check and release anyway