Broker creates EXDATE property with floating timezone

[KristofferFM]

If an organizer removes an attendee from a single instance of an recurrent event, and that event did not have an EXDATE property beforehand, Broker will add an EXDATE property with no timezone (i.e. floating timezone).
I believe this is wrong and should be fixed.