0) First, I wouldn't use a script task to import an excel file unless I absolutely had to. There is built-in importer functionality that makes it far easier to do.
1) I would create a separate importer package for each worksheet. Why? Because SSIS error reporting sucks wild donkey schlongs, and a failure anyplace in the importing process could crash the entire package, and thus cause the associated SQL agent to fail. It's MUCH easier to zero-in on failures when you have an agent that runs a "step" for each package. The only possible downside to this is that the filenames and worksheet names must always be the same name, and the sheets must always have the same columns formatted the same way.
2) If you insist on using a script task (again, I suggest you don't do this), I posted an article over the weekend that allows you to load an excel file (WITHOUT USING EXCEL INTEROP) into a
DataTable
that can then be used to move the data into a database -
CSV/Excel File Parser - A Revisit[
^]