Hi ssquire,
I think you are confusing native applications with web applications.
GWT is just a web toolkit provided by google. It is intended to run in any modern browser (IE, Chrome, Firefox, etc). It is just one of many possible web layer technologies that you can use to build your web pages. Your web page runs in a web browser and communicates to the server over HTTP. On the server (Tomcat, etc) is where the Spring technology exists. The server is probably at a web hosting provider, not running on the local machine or device.
Since the scaffolded GWT application is a WEB layer technology, it would only run on Android in a web browser, just like any other web application. As far as I know, any web application will run on android, as long as the browser supports that technology. I believe there are multiple browsers available on android, all of which most likely support GWT.
The scaffolding in MyEclipse G was going to build a native android application, not a web application. In a native application, the entire application is running on the device. No web browser, no server. There may be server synchronization options where data can be passed to a server or retrieved from a server, but the key is that there is no web browser necessary.
Even in the planned MyEclipse G product, there was no intent to create an android application that used Spring. All Spring tooling was to stay in MyEclipse for Spring. The MyEclipse G product was going to use Objectify and Google App Engine with SiteBricks. No Spring.
I hope this helps.