Local write skew check cannot work with persistence

The local write skew check is not based on comparing versions but object refences in container. If the entry is evicted/passivated during a transaction, the reference is removed from container and write skew check throws exception. Loading from persistence layer is insufficient as we load a copy of the instance.

Good thing is this may cause false negatives (spurious failures), but does not affect consistency.