I wanted to follow up on this. Turns out the problem was our use of the fixedThreadPool in OSGI. When we switched to cachedThreadPool the problem went away, and by putting JAMVM v1.5 on the system it became much more responsive. Sorry for the misdirect.
[Message sent by forum member 'drwatts' (drwatts)]