This is not so much an eForm issue but a MODx core issue. eForm utilizes the MODx vericode functions (or CAPTCHA if you will) and yes it needs cookies. Not so much for the vericode as such but for the keeping track of the session (which in turn stores the vericode).
Do you mean the cookies that using weblogin (a signed in user) provides???