Posing this question since one can not flow a transactional context as a
SOAP Header for an asynchronous web service invocation.
The WSIT TxClientPipe needs to detect that current invocation is
asynchronous AND expected to flow a WS-AtomicTransacationContext,
so appropriate action can be taken for this unsupported functionality.
-Joe Fialli