Comment 12 for bug 1526658

AFAICT, we only need to fix a module leak. Then there's only one module left (the correct one) to call.

It's obviously wrong that a client has all the client modules loaded for its lifetime...

I think Alan's comment #10 is a reasonable suggestion, but flawed. Because Mesa needs to load "mesa.so.3" to find the global symbol in question, not "libmirclient.so.9". So that would create a dependency in Mesa on the specific Mir driver version "mesa.so.3". And Mesa itself would have to change every time we broke the Mir client module ABI there. It's possible, but rebuilding Mesa and getting it into distro in time for a Mir release is a headache we don't need.