Conceivably, within Acrobat itself, you could either use an action or probably better, Javascript, to go through a directory (whether locally stored or on a network share), open each PDF file, invoke printing with predetermined print parameters, initiate printing, and close the PDF file moving on to the next PDF file in the directory.
However, this is a serial operation in term of opening the PDF file and generating the print stream. Once the print stream is generated, control is returned to Acrobat, i.e., Acrobat is not waiting for physical completion of printing, just the spooling to complete. And while this is happening, you cannot use Acrobat for any other tasks.
Actually in the scenario you describe, there really is only one instance of Acrobat, but it is serving multiple windows serially!
- Dov