In case anyone else ever needs to do this, here's the workaround I created:
1) Add a new field to the database called confString and fill it with random numbers for each photo
2) Add a new movie clip and a new MovieClipLoader object, below the boundaries of the movie, so it isn't visible when published.
3) Add the confString variable to the loadClip function that refers to the CFM page that pushes the JPG.
4) On that CFM, add the confstring check to the query that identifies the photo.
4a) If the query returns a record, run a query to update that record with a new, random confstring and push the file.
4b) If the query returns no records (ie the confstring is wrong), push a "Not available" image.
5) Add CFHEADER tags to the CFM page to prevent it from caching
6) Add a listener to the MovieClipLoader that, when the clip is finished loading, runs the new MovieClipLoader to load the same CFM page into the new movieclip, off the screen.
This will load the image, then load the "Not Available" image with the same file name, overwriting the file in the cache.
that's al. I doubt anyone will ever need this sort of thing, but just in case...
Joe