LegacyRegionManagerImpl#inactivateRegion calls lockManager.lockAll on the parent node,
so instead of just locking the parent while the region is inactivated, it locks the parent's
entire subtree (the entire cache if the region is a child of the root).
In combination with
JBCACHE-1608, this causes inactivateRegion to lock the parent's entire
subtree and never unlock it.