Give setMTOMEnabled higher priority for clients

Presently JBossWS clients call setMTOMEnabled to indicate if MTOM should be enabled for the call, however JBossWS then scans the known types for an @XmlMimeType annotation to decide if the call is eligible for MTOM.

The MTOM optimisation however applies to all binary types and not just the ones annotated with @XmlMimeType. The call to setMTOMEnabled should be sufficient to enable MTOM without requiring the check for @XmlMimeType