That looks to be a fairly reasonable idea overall then. You may want to double check that everything in the array is a file that's readable (maybe even check that its in a place you're allowing to be read from), then provide it as an argument.
An alternative is to use a single entry point, and provide querystring information regarding it. That's probably more along what I'd do, simply to save on processing files. I typically build lots and lots of classes, but only one executable file with only a few lines of code. Too bad PHP doesn't have a class entry point.
If these were classes, than the better approach is to use autoloading with registered extensions. That's a simple matter of adding an include path, and registering the extension (which is why I always suggest .class.php as your php class files and interfaces). Then it's automatically discovered in the include path and included on invocation of new:
set_include_path(get_include_path() . PATH_SEPARATOR . '/path/to/class/files'); // you can do this as many times as you want for multiple locations
// etc etc
Works with use commands as well so long as the fileystem structure matches the namespace. So then I can
and it automatically resolves so long as the parent directory to \namespace is registered. Neato.