Refactoring WSDL leads to two namespace declarations

I am the lead QA person on a versioned WSDL, and I'm currently trying to figure out how to refactor my SoapUI regression testing project to a new version of the WSDL. When I use the refactoring tool built-in to SoapUI Pro, I end up with two xmlns declarations at the top of each request. As an example, I am trying to go from version 9.0 to 10.0. Here's what I see before and after refactoring:

Before:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="https://myurl.com/Web.Services.Interfaces.9.0">

After:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="https://myurl.com/Web.Services.Interfaces.9.0" xmlns:ns1="https://myurl.com/Web.Services.Interfaces.10.0">

Is there any way I can just replace the namepsace entirely, rather than appending another namespace onto the end, so that the only namespace is ns and it points to the 10.0 version of the WSDL?

Thanks!