clustered and covering index ignored on delete statement. Table scan occurs
The optimizer may find a scan more appropriate based on statistics on the duplicate index instead of statistics on the PK. You didn't define the duplicate index as UNIQUE, so getting the "good" or "bad" plan could be just a matter of which index metadata is used by the optimizer to produce the plan.
Very hard to tell without the actual execution plan, though.