Avoid calling Thread.getContextClassloader() to improve performance

When a Drools instance is deployed into Gigaspaces container with the Java Security Manager enabled, accessing the context classloader is an extremely heavy operation (over 400 times slower) and also causes thread contention among different threads running different sessions. In order to work around this problem, change the code to avoid accessing the context classloader as much as possible, without compromising thread safety.