Currently I am working on Spring+Tomcat. Previously we were working on weblogic + spring, that's where the ~50% CPU time measurement came from.
The project where I found myself the most frustrated with Spring was in a simple console app, where Spring became the server container. The application was more or less empty, having only a few database connections, and it took probably about 10 seconds to boot up. I really remember thinking "this is as fast as it will ever be" it only got slower from then on.
I would not judge Spring the Framework by Spring the IDE (which is a bunch of plugins on top of Eclipse). The Spring integration in IntelliJ is great.
Your bad experience was with a Spring-branded Eclipse; the open-source IDE that's so slow and bloated Google preferred switching to a proprietary competitor (IntelliJ) for their latest version of the Android IDE.
This framework really redefined my notion of bloated, although to be fair, i really don't know if the runtime and API part of the framework gave me that feeling, or if it's not mainly due to the extremely painful development environment (aka spring sts : one JVM for the IDE, one JVM for the bean execution, and one virtualization layer on top of the web server thanks to VMWare vFabric...).
In the end, it took me more than 5 minutes to boot STS and get the server run my code, on my fairly recent 4G of RAM MBP.