It might actually be the "Create Object" piece. Click the Help button for Create Object and you will notice that this happens Immediately. So, probably what is happening is that the event fires, Create Object happens immediately, then the sequence begins which fires off a 2nd Create Object after the Destroy Object. So that equals 2. Logically, this sounds like it is what is happening instead of being a bug. So, you probably need to do this differently (like what worked for me) in this particular case.
Below is from the Help.
The object is created IMMEDIATELY, before other actions are called on the state. If the created object has an FSM, that FSM also becomes active IMMEDIATELY, before other actions on the state.