LUCENE-5553 can prevent ReaderClosedListener from being called if the indexreader is closed and the shard was already closed or relocated. This has been fixed in Lucene 4.7.1 and will be part of the next bugfix release for the 1.1.x series. We can't backport this to the 1.0.x series since this branch is running on LUCENE_46

The problem with this bug is that we never release the fielddata or filters that are associated with the index reader that runs into this bug. If the index is moved away from a node the memory is free again as well as during shard cleanups so in production this might not be a huge issue. Yet, there are node level services like the circuit-breaker that relies on the ReaderClosedListener to be invoked to adjust memory which can report wrong memory consumptions for the rest of it's lifetime.