This depends on how much work you want the template to do. It's one thing to create a session and provide it to the template. It's another to have the template do all the work.

FWIW, I tend strongly toward the first option. Decoupling the display of the data and the manipulation of the data will pay off in the long run. (perrin always has good arguments about this on the relevant mailing lists)

That said, the Apache::Template module is very straightforward and encourages this sort of action, since it's template-driven rather than code driven. Creating a session plugin would be fairly simple and wouldn't seem to affect much else. So I'd say go ahead and create it -- since it's independent it shouldn't be too much trouble to replace it later if you find it doesn't meet your needs.

Chris
M-x auto-bs-mode