+1'd Marek's answer - definitely look through those resources.
Some points...
You're definitely right to try this, even in a small app. Its also important to think hard about superficially simple questions like the one you posed. For DI, you really do have to actually do some work with it to really appreciate it - I for one was in the "Oh, I've only got a small app" (denial) camp for a long time until I actually used it.
There's a school of though that one in general should be steering away from Service Locator and just having injection [without any dependencies on a container].
If you dont use Service Locators, nobody needs to know where the Container (Kernel) is, which is the best thing.
Modules are mainly for the purposes of compartmentalising batches of things to register in a particular overall Container (Kernel).
Surely there's a canonical 'Global Container' Singleton implementation out there for Ninject? EDIT: Just found one:- http://www.codethinked.com/post.aspx?id=8e162def-7b67-4bc1-9fa2-87bbeb356104
See also http://stackoverflow.com/questions/1651174/ninject-how-do-i-inject-into-a-class-library/1653708#1653708