Use of o.s.c.r.composer.RESTEasyMessageComposer causes leak of Camel data in response headers. Please see attached example project for reproduction of issue.

A request to /exampleServices/exampleService will show response headers such as CamelMessageHistory, CamelToEndpoint, and org.switchyard.messageId. This seems to be a security risk. A similar request to /exampleServices/exampleServiceToo omits these headers.

jmorales in the Switchyard IRC on freenode commented that this should be opened in JIRA. Please let me know how I can be of assistance.