This makes sense since it would allow tasks to run in parallel.
While the CFHTTP tag wants to run in serial, we can finagle it to run in "parallel" by making sure that its timeout is low (one second).
In doing so, we can trigger each task with its own CFHTTP tag while not having to wait for the previous CFHTTP tag to return. We still have one Cold Fusion scheduled task that runs every few minutes.
To see an example task, complete with meta Data, take a look at the following code.
This code would periodically email a girlfriend to let her know how wonderful she is.
For convenience, the run page assembles a task Data object to pass into the module during execution.