Chrome launches many processes as a normal matter of operation. The program itself requires two or three and you will also find one for every open tab and plugin. It's not uncommon to see half a dozen when using Battlelog. This isn't a fault of Battlelog but rather just how Chrome works.
The idea behind it is if one process experiences a critical error, such as if Flash were to crash, your browser and all other open tabs aren't affected. In a browser that does not offer process isolation, that would usually result in the entire browser crashing.
If you launch Battlelog in a different browser that doesn't use process isolation such as Firefox, you won't observe that behavior. Nothing is wrong, however.
I did not want to reward your obvious posting of this in an incorrect, high-traffic section for exposure, but my desire to answer the question won out.
Edited by Particle - 11/14/13 at 6:24am