Conference: participant info takes a few seconds to update when a participant is removed
The body of the video mixer's source-info-update-callback gets queued into the main job queue behind some call destruction tasks and induces incorrect conference participant metadata in the interim.
- Why is call destruction so long?
- Dirty fix: use a thread pool?