Currently StandardJarScanner.process calls org.apache.tomcat.util.scan.JarFactory to create a org.apache.tomcat.Jar instance. Our new nested jar code will result in org.apache.tomcat.util.scan.JarFileUrlJar which is not very performant. We might be able to create our own Jar implementation and a StandardJarScanner subclass to use it.