?
This is not possible with that setup. If the DLLs are deployed separately at times, they should really be their own deployables (or even applications in some cases), that way you can specify them to be deployed at the release level.
However, for your case, you may be able to get away with creating multiple variables (e.g. FILEMASK1, FILEMASK2, FILEMASKN, etc.) I'm not actually sure if that will work or not, and still wouldn't solve the problem if you have more than N files.