Indeed, the scheduler will remove all relevant exception events if the series is updated or removed. This can be observed in our online demos
using Network tab of the browser developer tool
The only reason that I can think of, for not deleting the exception events, is the exception events does not point to the recurrence head event (recurrenceId field is not updated correctly). Would it be possible to send us a simplified repro demo that demonstrates the issue?