Removal of inherited PersonHasESet entries cause delayed removal of child PersonHasESet entries, DBScheduler does not remove those during first calculation of AllForOnePerson. Subsequent calculations of e.g. AllForOnePerson or PersonHasESet successfully remove child PersonHasESet entries. This may include ESets which are provided through an ITShop request.
You can trigger a recalculation for affected persons using the SQL statement
exec QBM_PDBQueueInsert_Single 'QER-K-AllForOnePerson', '<UID_Person of affected person>', '', 12345
which queues a job for inheritance recalculation for the affected person.
Development has acknowledged and fixed bug #25853. The bug affects 7.0.x and we can provide a fix through a support service request. Version 7.1.0 and later are not affected.