Thanks Steve
I found a similar recent case for 10.0/IBM JVM 1.6 which also had repeated entry point detection (uses dynamic instrumentation) symptoms in the logs
[IntroscopeAgent.EntryPointDetection] Initial Entry Point Candidate
[IntroscopeAgent.EntryPointDetection] Removed Inactive Frontend Candidate
If you see similar messages our customer found that using the NoRedef profile/AgentNoRedefNoRetrans.jar fixed it although you could try to disable entry point detection if you are happy to do that? i.e. introscope.agent.deep.entrypoint.enabled=false
Entry point detection is enabled by default in both 10.0 & 10.1 so that still does not explain why you only see the problem in 10.1 !
Regards,
Lynn