Hello, Jack.
Actually, I have just the same issue. Unfortunately, I can not post code here, because this is closed project, but I will try to explain all in details. I have some loading factory, which uses LoaderMax and ImageLoader as items of LoaderMax queue. Everything is pretty easy - I have one loading queue (Loadermax), and adding ImageLoader instances into it. First of all, from what I understand noCache property is set to true for ImageLoader by default, which is a little bit strange at least for me, because you typically want images to be cached by the browser and not reloaded each time. In my case, it caused each image to load 2 times (I am really not sure why, this is something I see in FireBug, this double loading, and I definitely adding only one instance of particular ImageLoader per one image. Maybe, it interfere somehow with the fact, that i do no have direct urls of images - meaning that the urls does not represent direct location of image on the server. The urls are dynamic, consisting of base url and image id, and the server returns correct image based on the id). Anyway, setting noCache property to false to each ImageLoader instance does not remove gsCacheBuster part from the final url. The final url also contains purpose=audit part, and this is related to auditSize property of the LoaderMax. Setting defaultAuditSize static property of LoaderMax to false removes both gsCacheBuster and purpose=audit parts from final url, making this url just what I wanted. However, this caused another issues. For some reasons, crossdomain policy file is not loaded anymore (again, this can be "fixed" just by not setting defaultAuditSize to false), and the rawContent property of the ImageLoder becomes of type Loader instead of Bitmap. Also, not sure whether this may be important or not, the images are loaded from https, not http. But anyway, it's a little bit weird that setting or not setting defaultAuditSize influence all this stuff.
Ilya