I was able to solve my problem using this web.xml configuration ...
<servlet>
<servlet-name>dispatcher</servlet-name>
<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
<init-param>
<param-name>contextConfigLocation</param-name>
<param-value>/WEB-INF/jboss-as-spring-mvc-context.xml</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>dispatcher</servlet-name>
<url-pattern>/dwr/*</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>dispatcher</servlet-name>
<url-pattern>/</url-pattern>
</servlet-mapping>
and this Spring MVC config ...
<bean class="org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter" />
<!-- DWR will scan all Spring managed beans containing @RemoteProxy or @RemoteMethod
annotations and register Creator proxies for them. This will NOT scan any
classes not managed by Spring. -->
<dwr:annotation-config id="springdwr" />
<!-- DWR will scan the classpath and search classes containing @RemoteProxy
or @RemoteMethod annotations. This will register the beans and Creator proxies
for these classes. -->
<dwr:annotation-scan base-package="org.collegeboard.springboard"
scanDataTransferObject="true" scanRemoteProxy="true" />
<!-- DWR will map util.js and engine.js files to the dwrController. You
can then include this files as external Javascript references from your JSP -->
<dwr:url-mapping />
<!-- Defines the dwrController. During production, set the debug property
to false -->
<dwr:controller id="dwrController" debug="true" />
<!-- This is required if you want to configure any beans not managed by
Spring. Leaving it enabled doesn't do any negative effects. Here's a sample
config: -->
<dwr:configuration />