cc-control is a forking daemon -- it starts a new process for each connection. So it's perfectly normal to see multiple cc-control processes.
If those processes are consuming a lot of CPU time for a long period of time, though, it's likely that something has gone wrong and that would be a bug. Have you noticed any particular actions within Centova Cast that trigger a cc-control process to start eating CPU time?