I think my point is: usually, when there's documentation that says that a service is loaded using three classloaders—or other kinds of documentation related to files or configuration discoverable in multiple ways—there is an implicit understanding that the process will stop as soon as one of the described mechanisms succeeds. In this case, the discovered item is created three times, and then two of them are thrown away. Then the one that is used is cleaned up three times. There is a lot that is strange here.