The WebApplication uses the MostRecentlyUsedMap as a limited size cache. Elements of
the cache are removed when a new entry is added based upon the age of the element's keys
not on the age of the element's data.
Naively, I would expect a high usage element (one's whose associated data keeps changing)
should be kept in the cache rather than reaped - simply because it was enter earlier than some
low activity but more recent entry.
The MostRecentlyUsedMap is based upon the Java LinkedHashMap container.
As such, it is not a very good fit for data-based age cache.
Of course I could be completely wrong in this case and it actually the age of the key that is
important not how often the data associated with the key is changed.