Does a lot of the same stuff as PersistentBloatContext except that
it manages the chaches of BLOAT objects. For example, when a
MethodEditor is no longer needed, it is removed from the cache if
it is not dirty. This context is meant to used in volatile memory.
Constructor.
Parameters: loader - Used to load classes Parameters: classes - Some initial classes in the context Parameters: closure - Do we look for the maximum number of classes?