Common Services Level 2 reviewed the Tomcat log after LOGLVL='+T' was added and from the CCS perspective the Tomcat environment appeared to be OK.
The Web Viewer group advised that one way to determine if Web Viewer is causing the memory concern is to set up and run Tomcat Manager and 'undeploy' the Web Viewer application along with CA Styles. Knowledge Base article KB000012737
provides instructions on how to do this. When this was done a decrease in the CPU activity was noted. Web Viewer Level 2 suggested additional tracing steps and a console dump of the Tomcat STC at a point where the customer sees CPU activity occurring. Review of the dump showed that the main thing taking storage and resources was the JVM associated with the Tomcat task.
The OM Web Viewer group suggested an upgrade to Java 1.8. In his next update, the customer advised that the Java upgrade provided a significant decrease in memory usage.