Github user Randgalt commented on the issue:
https://github.com/apache/curator/pull/243
@egor-ryashin For `LeaderLatch` calls `setLeadership(false);` when the
connection is lost. `LeaderSelector` is a bit more complicated but if you use
the recommended `LeaderSelectorListenerAdapter` the active leader will get
interrupted when the connection is lost which will result in a release of the
its internal lock. In both cases the lock node (`A` in your example) gets
deleted on connection loss.---
