OK, I'll start the fake application in its own class loader.

On a side node, the test is already using a new classloader to run the essential action:
```scala
val testClassLoader = new ClassLoader(){}
Threads.withContextClassLoader(testClassLoader) {
  action.apply(FakeRequest()).run
```
and thus, is already making sure that the running application change the classloader to execute the essential action.

The fact that the class loader of the running application is the one of the current thread is not a problem IMHO.