Yes.
The trick is Virtual Memory. Did you know a 16 bit PDP-11, where any given program could only address 64K (65,536 bytes), that PDP-11 could have up to 4MB of physical memory. A PDP-11 ran UNIX (as does Mac OS X), and the PDP-11 UNIX kernel could only address 64K at a time, but it was able to work on a system with 64 times as much memory. The PDP-11 used was an early form of virtual memory.
The Mac OS X operating system creates a virtual memory map for each process that is run. It will populate that virtual memory map with the physical address of as many 4K memory pages as is needed for that application. Since each applciation has its own virtual memory map, you can have 100's of processes that are capable of consuming all of your 8GB of memory (or more).
The Mac OS X operating system for the most part only needs to play with some numbers that represent physical memory addresses and put them into an array that happens to be a virtual memory map. The Mac OS X operating system does not need to actually look at all that memory all at once.
When Mac OS X needs to access a process' memory, it just uses the virtual address map previously created. When it has to access the memory of a different process, it switches to that processes virtual address map.
If you happen to have an application compiled for 64bits, then Mac OS X will create a 64 bit virtual memory map for that application. When Mac OS X needs to access any part of the 64 bit applications address space, it can either switch to a little bit of 64 bit capable code of its own and use the application's 64 bit virtual memory map to access that data, or it can modify its own kernel 32 bit virtual address map, so that a small portion of the kernel's 32 bit address range is using the same physical addresses as the part of the 64 bit process the kernel needs to access.
This is a old operating system trick that has been around since virtual memoy was invented. One of my early jobs was writing a virtual memory hardware diagnostic back in '75, and we were doing this kind of thing back then, and virtual memory pre-dates that.
So yes, a 32 bit kernel is perfectly capable of using more than 4GB of physical memory. And a 32 bit kernel is more than capable of servicing 64 bit applications.