HTTP Health Monitor fails when New Relic Browser enabled and using a Receive String

Trying to enable New Relic Browser in a JBoss application server. Our F5 unit has a built-in HTTP health monitor that is working when New Relic Browser is disabled.

When New Relic Browser is enabled in the application, the built-in HTTP health monitor fails. Able to cause this health monitor to fail by dynamically turning on New Relic Browser and succeed by dynamically turning off New Relic Browser.

The health monitor queries JBoss' JMX Console for deployments in the JBoss container:

Interval: 30
Timeout: 90
Reverse: No
Transparent: No
Send String: GET /jmx-console/HtmlAdaptor?action=displayMBeans&filter=jboss.web.deployment\r\n
Receive String: myapp

Has anyone else run into an issue with the built-in health monitor when New Relic Browser is instrumenting the pool member?

Does the built-in HTTP health monitor have a size limit on the response?

Else, what steps are needed to debug the built-in HTTP health monitor?

This following page seems promising since curl and GET work fine within a couple of seconds yet the built-in HTTP monitor fails. Would think the built-in HTTP monitor should handle such a simple request but maybe missing something fundamental. HTTP Monitor cURL Basic GET https://devcentral.f5.com/codeshare?sid=395

Background: With New Relic Browser enabled, New Relic Agent injects a long scriptlet inside the head of each HTTP document. The scriptlet starts out like so: