Update Definition updates requests it shouldn't

Using 2.0 Pro final, we've found that Update Definition, when only "Create New Requests" is checked(and there may be other combinations), sometimes still updates existing requests.

Sometimes it will wipe entire requests, replacing it with the default request. Mostly, though, it just adds missing elements. The least occurring result is that it does what I want.

For example, a snippet from one of my requests, before definition update:

<doc:requestHeader>  
  <doc:requestor>soap-ui</doc:requestor>               
</doc:requestHeader>

After an update(which didn't actually have any changes in it)

 <doc:requestHeader>  
  <doc:businessTransactionId>?</doc:businessTransactionId>
               <doc:requestor>soap-ui</doc:requestor>
               <doc:responseRequired>?</doc:responseRequired>
               <doc:transactionEffectiveDateTime>?</doc:transactionEffectiveDateTime>
               <doc:transactionId>?</doc:transactionId>
               <doc:transactionSubmitDateTime>?</doc:transactionSubmitDateTime>
</doc:requestHeader>

It also does this even when I don't check any of the check boxes on the update definition dialog.