Client in WSDL mode drops WS Security header when posting

Greetings alll,

I'm working with wsf-php to interact with some web services on a PeopleSoft system.  I have the entire architecture put together and it's working wonderfully as long as I am working anonymously but when I attempt to use a standard WS Security policy with Username Token (user and password) it simply doesn't put it in the SOAP Headers.  I've pointed it to a local non SSL server so I could get a packet trace and verified that the security headers are just completely missing.  When I use the same CI with SoapUI and send the following headers it works fine.

<soapenv:Header>

<wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">

<wsse:UsernameToken>

<wsse:Username>PS</wsse:Username>

<wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">PS</wsse:Password>

</wsse:UsernameToken>

</wsse:Security>

</soapenv:Header>

The code I'm using is:

  $security_options = array("useUsernameToken" => TRUE );

  $policy = new WSPolicy(array("security" => $security_options));

  try {

          $security_token = new WSSecurityToken(array("user" => "PS",

                                                        "password" => "PS",

                                                        "passwordType" => "Digest"));

        $wsclientArray = array(

             "wsdl" => "/tmp/CI_MESSAGE_CATALOG_CI.1.wsdl",

              "useWSA" => TRUE,

              "policy" => $policy,

              "securityToken" => $security_token);

          $wsclient = new WSClient($wsclientArray);

          $client = $wsclient->getProxy();

         // we do this to get the memberId

          $responseArray = $client->CI_MESSAGE_CATALOG_CI_G ( $request );

var_dump ( $responseArray );

    } catch (Exception $e) {

          $memberID = 0;

    }

I also attached the snippet of WSDL that specifies the security policy as I'd noticed a few posts about using the client in WSDL mode with mismatching WSDL policies:

<soap:operation soapAction="CI_NBW_ADM_APPL_ENTRY_CI_UD.V1" style="document"/>