WSN2005 with CXF-BC: Weird namespaces for nested elements

For a notification producer and consumer using the wsn-cxf-binding example contained in ServiceMix 3.3.1, if the schema for a message sent via notify() from the broker contains nested elements in a complex type, namespaces xmlns="" and xmlns:ns="http://www.w3.org/2005/08/addressing" will unnecessarily be added. Example message:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns2:Notify xmlns="http://www.w3.org/2005/08/addressing"
xmlns:ns2="http://docs.oasis-open.org/wsn/b-2"
xmlns:ns3="http://docs.oasis-open.org/wsrf/bf-2"
xmlns:ns4="http://docs.oasis-open.org/wsrf/rp-2"
xmlns:ns5="http://docs.oasis-open.org/wsn/t-1">
<ns2:NotificationMessage>
<ns2:Topic Dialect="http://docs.oasis-open.org/wsn/t-1/TopicExpression/Simple">WeatherReport</ns2:Topic>
<ns2:Message>
<ns7:weatherReport xmlns:ns7="http://test.org">
<ns7:weather>
<location xmlns="" xmlns:ns7_="http://www.w3.org/2005/08/addressing">St. Mary Mead</location>
<temperature system="Celsius" xmlns="" xmlns:ns7_="http://www.w3.org/2005/08/addressing">15.0</temperature>
</ns7:weather>
</ns7:weatherReport>
</ns2:Message>
</ns2:NotificationMessage>
</ns2:Notify>
</soap:Body>
</soap:Envelope>

An equivalent message produced by Fuse Services Framework 2.1.3.1 would not contain these namespaces.