Injecting the context is available in bean services (@Service), but it's not available in beans that are called directly from a Camel route (@Named). I would think that Camel message headers would propagate to the SY reference being invoked - in this case, the SOAP binding. This would mean that you could set the Camel message header inside your route and that should get mapped to the context for the SOAP reference binding. If this doesn't work, then it's a bug.
In terms of mutual SSL auth, you can accomplish this directly with the JBoss AS 7 https connector. I believe the appropriate attribute on the https connector config is "verify-client".