It appears that is an issue... thanks for bringing it to our attention.
The solutions are to either;
1) Don't update the email field value by editing the Update Record server behavior and removing the email
2) Adding unique column value validation to the email field so that the same email can't be entered if it is already used. The unique id of the users table will be accessible from: <?php echo($_GET['fp_id']); ?>, so you could use that in the unique column validation setting.
We will have to update the wizard to correct for this problem. I'm leaning toward removing the email field entirely in the update process since really this is for updating your password and not your email in the first place.