Sounds like a job for a recursive loop in custom code.

The good news is that if this is a one-time need, you can just create an
aspx to get the job done (rather than messing with a whole feature
deployment).

To add to that, here's what I've got:

- A powershell script (setting the execution policy to disabled)
- Loading the Microsoft.SharePoint, and Microsoft.SharePoint.Publishing
assemblies.
- Reading a text file, and creating the sites/subsites based off what I've got
in there.

...still searching for the magic that will enable  me to do this. Ideally, I'd
like to stick to doing it with powershell. If that's not an option, I'm open to
any means to get it done!