The AGPL-motivating issue doesn't seem to apply here. That covers the case where someone builds (for example) a website using GPL'ed components, but doesn't distribute the server-side and therefore doesn't have to release the source code. (In your case, you ARE distributing your framework.)
There is a caveat to the above. If the libraries are LGPL or "GPL with Classpath exception" then non open-source code can effectively use the libraries without being "contaminated" by the "viral" GPL release requirements. Check the licenses for the libraries you are actually using.
The bottom line is that you need to understand what the licenses yourself, make your decisions on that basis, and live with the consequences. If you want to distribute binaries / bytecodes without releasing your source code, don't use GPL libraries. Period.