Thanks for the info.
I assume multiple JARs problem could be resolved with using AS runtime to determine the JARs which are on the classpath for the given deployment.
Full debuggability of the complete AS source would be killing feature!