Invalidation mode caches with pessimistic transactions results in stale remote locks

An invalidation mode cluster with two nodes A and B. Node A is coordinator.
Putting a key on node B results in a remote lock being acquired on A. But the lock on A is not released when the TX commits. Subsequent attempts to lock the key on A will fail with TimeoutException.

The key aspects to reproduce this are:
1. pessimistic locking
2. the transaction starts on a node different than the coordinator

This scenario does not involve any state transfer, so it should not be related to the already known issues with stale locks caused by state-transfer.