We seem to be talking about three different issues here:
1. The issue that Mark's commit fixed - potential for memory leak when the class loader for the eviction thread is not the same loader that loaded the library. IIUC, Mark's patch fully fixes this issue and any other potential for classloader leaks associated with the evictor. Correct?
2. Feature request to support the use case in the issue description. Looks to me like Mark's patch actually does fully fix the issue as narrowly defined above. I must be missing something here.
3. Feature request for pool to work in arbitrary multi-classloader environments
I agree with Mark that it is not obvious that we should aim to support 2., and I think we have some work do to in defining exactly what 3. means. I am strongly +1 on doing everything we can to avoid leaks.