OSGiIsolatedScriptingContainer scriptingContainer = new OSGiIsolatedScriptingContainer();
// to avoid verify errors with bouncy castle jars
scriptingContainer.setClassloaderDelegate(false);

we did revert this default on regular jruby runtime to delegate class loading to the parent classloader. there were basically two main reasons for this:
nokogiri using xalan from the jvm which is fixed now with sparklemotion/nokogiri#1212

and joda-time could conflict when joda-time gets required by a runtime - and there is not work around beside ignoring the require on a jruby runtime.

my intention here is more the OSGi case, if I add jruby to an OSGi I just expect it to work and seeing class verify errors on bouncy-castle classes feels like a serious issue.