<issue_start><issue_comment>Title: acquireLeadership to go to maintenance mode does not have a corresponding destroy
username_0: When ehcache is put to maintenance mode it does an acquireLeadership..but there is no corresponding call to abandonLeadership. This may cause the VoltronReadWriteLockEntity once the cluster tier manager for a given entity identifier is destroyed.
<issue_comment>username_0: A second side effect of this bug is that even after a cache manager with a given identifier is destroyed, its corresponding VoltronReadWriteLockEntity will remain in the system, causing an entity leak in the platform (esp. if the same identifier is not reused for the same cache manager).<issue_closed>