I would like to use Castle Windsor for dependency injection for my solution consisting of the following projects:
You have to ask yourself one thing: "do I really need 4 different assemblies for my MVC project?" You should break the code into assemblies according to deployment boundaries, not just based on some vague notion that Model code should be physically separate from Business code & similar. You should use namespaces for such things instead of separate projects.
Here's a good article on this issue: Advices on partitioning code through .NET assemblies by Patrick Smacchia.